Implement Streamable HTTP transport#33
Merged
topherbullock merged 12 commits intomodelcontextprotocol:mainfrom Jun 13, 2025
Merged
Implement Streamable HTTP transport#33topherbullock merged 12 commits intomodelcontextprotocol:mainfrom
topherbullock merged 12 commits intomodelcontextprotocol:mainfrom
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements a rack-compatible Streamable HTTP transport with SSE support. As well as add notification support for the server with the following methods:
notify_tools_list_changed()- Send a notification when the tools list changesnotify_prompts_list_changed()- Send a notification when the prompts list changesnotify_resources_list_changed()- Send a notification when the resources list changesCloses #4
Motivation and Context
To fulfill the Streamable HTTP transport specification as described here.
How Has This Been Tested?
Local tests only (see
examples/). Working on implementing it with my MCP server that's a WIP.Breaking Changes
Should introduce no breaking changes as using the StreamableHTTP transport is optional
Types of changes
Checklist
Local Tests